Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-developer is "full-text-search-within-gps-area">
    <p>It allows to retrieve the geolocated entities (not only services) that match with a list of keywords. The results can
        be possibly filtered to be within a rectangular area </p>

    <h3>Inputs</h3>
    A JSON with these parameters:

    <dl class="message-properties">
        <dt>latitudebottomleft
            <span class="property-type">number</span>
        </dt>
        <dd> latitude of the Bottom Left Point of a rectangular area.</dd>
        <dt>longitudebottomleft
            <span class="property-type">number</span>
        </dt>
        <dd> longitude of the Bottom Left Point of a rectangular area.</dd>
        <dt>latitudetopright
            <span class="property-type">number</span>
        </dt>
        <dd> latitude of the Top Right Point of a rectangular area.</dd>
        <dt>longitudetopright
            <span class="property-type">number</span>
        </dt>
        <dd> longitude of the Top Right Point of a rectangular area.</dd>
        <dt>search
            <span class="property-type">string</span>
        </dt>
        <dd> the keywords separated with spaces that have to match with any textual description associated with an entity.g</dd>
        <dt>maxresults
            <span class="property-type">number</span>
        </dt>
        <dd> maximum number of results to be returned (if parameter is missing 100 is assumed), if it is 0 all results are returned</dd>
        <dt>lang
            <span class="property-type">string</span>
        </dt>
        <dd> ISO 2 chars language code (e.g. “it”, “en”, “fr”, “de”, “es”) to be used for returned descriptions if available in
            multiple languages. Currently for languages other than “it” and “en” it returns “en” descriptions. (if parameter
            is missing “en” is assumed)</dd>
        <dt>geometry
            <span class="property-type">boolean</span>
        </dt>
        <dd> true/false, if true it returns a “hasGeometry” property for each service stating if the service has a complex WKT
            geometries (linestring, polygon) associated with it (if parameter is missing “false” is assumed)</dd>
    </dl>

    <h3>Outputs</h3>
    <ol class="node-ports">
        <li>ServiceUri Array
            <dl class="message-properties">
                <dd> Returns an array containing the servicesUri of each service found</dd>
            </dl>
        </li>
        <li>GeoJSON Results
            <dl class="message-properties">
                <dd> the results format is a GeoJSON “FeatureCollection” with the matching entities, additionally the “fullCount”
                    property provides the full count of results available matching the query. For each “Feature” a minimal
                    set of properties are provided</dd>
            </dl>
        </li>
    </ol>

    <h3>Details</h3>
    <p>The node can receive a JSON with the parameters described in the Inputs section and with them generate the output JSON.
        If the values are not present in the input JSON, these are read by those in the configuration. If they are not present
        in either part, an error is generated for the necessary parameters.</p>